Merged
Conversation
zuston
approved these changes
Nov 23, 2022
Member
|
Welcome @leixm @xianjingfeng @smallzhongfeng |
Codecov Report
@@ Coverage Diff @@
## master #351 +/- ##
============================================
- Coverage 61.37% 58.42% -2.96%
- Complexity 1529 1554 +25
============================================
Files 186 193 +7
Lines 9445 10758 +1313
Branches 924 935 +11
============================================
+ Hits 5797 6285 +488
- Misses 3340 4102 +762
- Partials 308 371 +63
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Member
|
Thanks |
Contributor
|
Thanks. |
Contributor
|
Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub
Projects may assign external (non-committer) collaborators the triage role for their repository.
The triage role allows people to assign, edit, and close issues and pull requests, without giving them write access to the code.
I add active contributors to the collaborators list.
Why are the changes needed?
It's convenient for the active contributors to manage issues.
Does this PR introduce any user-facing change?
No
How was this patch tested?
No